Skip to content

chore: Generated Files.FileUploadRequest resource#1274

Open
osmanhadzic wants to merge 1 commit intoedgehog-device-manager:mainfrom
osmanhadzic:feat/file-upload-request
Open

chore: Generated Files.FileUploadRequest resource#1274
osmanhadzic wants to merge 1 commit intoedgehog-device-manager:mainfrom
osmanhadzic:feat/file-upload-request

Conversation

@osmanhadzic
Copy link
Contributor

Generated the Files.FileDownloadRequest resource using the command

mix ash.gen.resource Edgehog.Files.FileUploadRequest \\
  --default-actions read,destroy \\
  --uuid-v7-primary-key id \\
  --attribute url:string:required:public \\
  --attribute source:string:public \\
  --attribute compression:string:public \\
  --attribute progress_enabled:boolean:public \\
  --attribute status:string:public \\
  --attribute progress_percentage:integer:public \\
  --attribute response_code:integer:public \\
  --attribute response_message:string:public \\
  --relationship belongs_to:device:Edgehog.Devices.Device:required:public \\
  --timestamps \\
  --extend postgres,graphql

Change Title

Checklist

  • I have read the CONTRIBUTING.md
  • I have added tests that prove my fix is effective or that my feature works
  • I have added or updated documentation (if appropriate)

Further Comments (optional)

Screenshots / Demos (optional)

@osmanhadzic osmanhadzic requested review from OmarBrbutovic and lusergit and removed request for OmarBrbutovic March 9, 2026 11:58
@osmanhadzic osmanhadzic force-pushed the feat/file-upload-request branch from ab1f239 to 5b579cb Compare March 9, 2026 12:08
Copy link
Collaborator

@OmarBrbutovic OmarBrbutovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, I would suggest slowing down the merge of this PR. The overall implementation of the feature has been changing frequently, and it would be better to stabilize the approach first.

Please make sure to research and implement the backend logic, not just the Resource layer. Additionally, the required migrations are currently missing.

For reference on how to properly introduce a new resource in Edgehog, you can look at these PRs:

Generated the `Files.FileDownloadRequest` resource using the command

```bash
mix ash.gen.resource Edgehog.Files.FileUploadRequest \\
  --default-actions read,destroy \\
  --uuid-v7-primary-key id \\
  --attribute url:string:required:public \\
  --attribute source:string:public \\
  --attribute compression:string:public \\
  --attribute progress_enabled:boolean:public \\
  --attribute status:string:public \\
  --attribute progress_percentage:integer:public \\
  --attribute response_code:integer:public \\
  --attribute response_message:string:public \\
  --relationship belongs_to:device:Edgehog.Devices.Device:required:public \\
  --timestamps \\
  --extend postgres,graphql
````

Signed-off-by: Osman Hadzic <osman.hadzic@secomind.com>
@osmanhadzic osmanhadzic force-pushed the feat/file-upload-request branch from 5b579cb to 941f8dc Compare March 9, 2026 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants